Random Time Management
As promised in my last post, here’s the method I am using at the moment with great success. You need a random-number generator to work it. The one I’m using is at http://www.random.org/integers/
I am using paper and pen, but I’m sure it can be adapted for electronic use. I just haven’t yet attempted to do so.
I’m using a loose-leaf binder with lined pages of 32 lines, but the method will work perfectly well with a bound notebook and pages of any number of lines.
First I list all my tasks in the notebook - one per line.
I then set my randomizer to produce integers in the range 1 and 32 inclusive. The upper number is the same as the number of lines on a page. This is just a convenient number which produces reasonable results, but you can use a lower or higher number if you wish. [Afternote: I now strongly recommend setting it for the number of lines on the page and not any other number]
Starting from the beginning of the list I use the randomizer to produce a number and move down the page that number of lines. I then do some work on the task on that line. Please note that I don’t have to finish that task, just do some work on it.
Once I have worked on the task, I cross it off. If I have not finished it or if it is a recurring task, then I re-enter it at the end of the list.
I then use the randomizer again and count to the next task (going to the next page if necessary).
When the number the randomizer produces would take me beyond the end of the list, I circle back to the beginning of the list, ignoring empty lines on the last page.
I continue circulating through the list in this way.
When I’m counting forward, I INCLUDE in the count the lines which have been crossed off. If I land on a line on which the task has been crossed out, I move to the next line in which there is an active task. I call this movement a “slide”.
For example imagine I have the following tasks:
Email
In Tray
Invoices
Date of next meeting
Write report
Cash check
Tidy desk
Performance reviews
I throw a five, so I count down the list, remembering to include the crossed out lines. I land on the “Write Report” line. I then “slide” to the next active task which is “Performance Reviews”. Slides work slightly different from counting. If a slide takes you to the end of the page, you circle back to the beginning of the SAME page. So if “Performance Reviews” in the example had already been done, you’d have circled back to “Email” at the beginning of the page.
Email
In Tray
Invoices
Date of next meeting
Write report
Cash check
Tidy desk
Performance reviews
Counting crossed-out spaces and sliding are very important, because they have the effect of increasing the chances of the older tasks on the list being selected. Note that if you don’t include lines with crossed-out tasks in the count, then every task will have an exactly equal chance and there will be no preference for older tasks.
A few points to note:
1) Random numbers behave randomly. They don’t behave in the way we expect them to behave. If they did, they wouldn’t be random. You will find that you are constantly surprised by them.
2) The system as described has a built-in bias towards clearing the older tasks off the list. This means that nothing will stay on the list for very long. How long that is depends on the length of the list and the amount of time you can devote to working on it. If you want things to move on really quickly then keep the list short.
3) The random-number generator is quite indifferent to your priorities, wishes and time-pressure, so if something needs doing now - do it!
4) Any attempts to increase the probability of certain tasks being selected will result in the chances of all the other tasks being reduced. So I advise against it.
Comments (135)
<
And thought: Damn, I've got the perfect tool (arrived a couple of days ago) for this: http://frictionless.bigcartel.com/category/index-cards
One card per project. Hm...
First, I got into a bit of trouble Sunday because I had a looming deadline Monday which meant I had to break out of the random system just to work on the deadline project. That might have been because I only started the system on Saturday. I'm thinking that normally if the system is truly random with a bias towards older items, bumping up against deadlines won't happen. If it does happen, it might be a sign that I just have too much on my plate, which is a good thing to know. Of course, as in all Mark's systems, genuine emergencies must take priority - as always, if something needs to be done, do it.
Second, I'm wondering about dismissal. There really is no dismissal in this system, because there is never a time when I don't feel like doing a task. In AF1, if I got to a page with a few tasks and no tasks stood out to be acted upon, I would dismiss the whole page. In this system, if it's on the list it's going to get done unless there is some external reason for not doing it. I don't know if that means anything or not. I've been throwing everything at the list, and I love it. In fact, it's kind of addictive. I can't wait to see what comes up next, because there are a few favourites I want to get to. In a way, its unconsciously training me to populate the list with fun stuff I want to do. This new method is causing me to completely rethink the way I manage my tasks.
<< I had to break out of the random system just to work on the deadline project.>>
Whenever an exception to the rule pops up - and I rejig the rules to fit the exception - the system loses it's power. And then I lose trust in the system, and soon after, stop following the rules. I know that sounds childish, but it has happened time and time again. So either I follow the rules, and deal with the consequences and rewards, or find something else that works.
A suggestion for those that like doing things analog, I can recommend using a twenty sided die (they are available from most hobby stores)
You stated:
"4) Any attempts to increase the probability of certain tasks being selected will result in the chances of all the other tasks being reduced. So I advise against it."
I've been doing exactly what you advise against for years and it has saved my bacon each time. I'm working from my day's closed list that I've prioritized from a weekly list. When I'm stalemated, the game helps me to get back on track. Even though I'm temporarily stuck doesn't mean that I want to do any random task. By priming the deck, I'm still able to stay on track. I don't see why you'd advise against favoring tasks from your WILL DO closed list. This way I'm likely to draw close to the number of cards I need to complete the tasks. The ones that take longer get more cards than the ones that don't and I prime the deck to choose my CI sooner than later. The reason I'm doing this is to get unstuck. Once I'm unstuck, I can return to the list. I honestly don't see how this is a bad thing especially because I know it works perfectly for the times I need to get unstuck. OTOH, you might advise against it because your list is used for more than one day.
I know that you're going to say that I'm going to do the entire closed list anyway. That's my aim but I want to clear the most important things first in case something happens where I can't actually finish it. Also, I like to get the PITA stuff out of the way first. In fact, it's probably those PITA tasks that are stalemating me. I just need a few nudges that this game helps with.
I like to have one list (home & work). I wonder if it is suitable to use the 'slide' to go to the next task that can be done in the current context (if one randomly lands on an task that cannot be done)?
< When the number the randomizer produces would take me beyond the end of the list, I circle back to the beginning of the list, ignoring empty lines on the last page.>
Do you a) circle back to the first available task on the list or b) continue the count on from the top of the list? a) would seem preferable as it is simpler and seems to lend itself to the bias of addressing earlier tasks.
I continue the count on just as if the first page were appended to the bottom of the last page.
<< any thoughts on naming the system? >>
I suppose in the spirit of the system I ought to use the "Random Article" button, rather than the Featured Article of the Day. So here goes....
I proudly announce the name of the system to be:
The Remelsbach System.
Because otherwise all tasks have an equal probability. Counting the crossed-out tasks biases the system toward the tasks at the beginning of the list.
How about, "The Final Version ...2" :)
Now in the example:
In Tray
Invoices
Date of next meeting
Write report
Cash check
Tidy desk
Performance reviews
If I count the active tasks alone, there is 25% (1 active out of 4 active) chance of choosing ‘In Tray’. If I count all tasks, there is 12.5% (1 active out of 8 total) chance of choosing ‘In Tray’. If 25%>12.5%, isn’t there higher chances of selecting an old task by ignoring the crossed out items?
In the next example after some work we have:
In Tray
Invoices
Date of next meeting
Write report
Cash check
Tidy desk
Performance reviews
If I count the active tasks alone, there is now 33% (1 active out of 3 active) chance of choosing ‘In Tray’. If I count all tasks, there is still 12.5% (1 active out of 8 total) chance of choosing ‘In Tray’. If 33%>12.5%, isn’t there still higher chances of selecting an older task by ignoring the crossed out items?
I understand that the list grows with new tasks, unfinished items, and recurring items. But the larger the list the larger the denominator. But, it will always be 1 active task/ N_active > 1 active task/(N_active +N_inactive).
since: N_active < (N_active +N_inactive),
then: 1 active task/ N_active >1 active task/(N_active +N_inactive).
I’m not understanding the bias. And I feel as if Im missing something significant. Sorry for being a little slow here :) Maybe its how Im reading the rules? I’m eagerly looking to be corrected, because I feel as If Im going crazy.
At the moment, after completing or working on a task (which is a Page on the CP task list), I am resorting to inserting a strikethrough page immediately below the task I worked on, then moving the task to the bottom of the list. The strikethrough page then acts as a placeholder for the task I just worked on. If the Randomizer then hits that page, I slide to the next page.
Anybody else here using CP and that has a better implementation idea?
The chances of any one number coming up are of course exactly the same for each number.
What is different though is how many numbers relate to any one task.
At the moment my first active page has 9 active tasks on it. There are 32 numbers (lines) on the page, all of which will result in one of the 9 tasks being selected..
My last active page has 23 active tasks on it and 29 numbers (lines). So you can see that there is considerably less chance of any specific task on the page being selected.
If only the active lines were included in the count, then on the first page there would be 9 numbers relating to 9 tasks, and on the last page 23 numbers relating to 23 tasks. So there would be exactly the same odds for every task on all the pages.
This is important because with equal odds for each task, it can take an unbelievably long time for every task to be actioned. You can try the experiment of seeing how many throws it takes to come up with every number between 1-32 (which is what I have my randomizer set on). I can guarantee you will be surprised.
This made sense to me a bit. The slide ensures that ‘landing on a crossed off item slides you to the next active task’. Makes sense in terms of proximity. But if I’m moving FORWARD in the notebook to the next active task, doesnt that mean that items remaining on NEWER pages have a high chance of being selected?
I would think the only way to ensure older tasks are biased is to slide backwards (to tasks before or older than the crossed off item).
Mark:
My last active page has 23 active tasks on it and 29 numbers (lines). So you can see that there is considerably less chance of any specific task on the page being selected.>
My math must be incorrect but:
9 active tasks out of 32 lines: 9/32*100= 28%
and
23 active tasks out of 29 lines: 23/29*100=79%
So, isnt there higher chance of a task on the last active page being selected since more of the lines are open to being selected?
Suppose that your entire notebook had only the two pages you describe (the first page and the last active page). So that in total there are now 61 lines to land on (32 lines from page 1 + 29 lines on page 2= 61 lines total). And there are now a total of 41 active tasks (9 active tasks from page 1 + 23 active tasks from page 2= 41 active tasks).
My math gives:
41/61*100=67%
meaning 67% of the notebook is filled with open tasks. and the remainder, 33% will yield slides.
The only time slides create a bias is when there are more inactive tasks than open tasks. But that how will that happen if the list is always growing with new tasks?
Regardless, of the 67% of active tasks, still theres more weight on the second page (newer page) with open tasks.
But your chances of selecting any 9 tasks out of the 9 options on the first page is:
1/9*100= 11%
and your chances of selecting any 23 tasks out of the 23 options on the last active page is:
1/23*100=4%
The odds arent the same on each page. one has 11% odds and the other has 4% odds.
I want to clarify, that the randomizer’s lower and upper limits always remains the same. That is, it always selects a random number between 1 and 32 (in your notebook). I get that. Just like rolling a die with 32 faces. But from the math above, Im not understanding how theres a bias towards older tasks. It seems as if everything that is told is the opposit for me. Which means either my understanding of the rules are messed up or my math is incorrect.
I realize this is annoying. But the system seems interesting and I would like to understand it rather than be using it and ‘believe’ its working. I appreciate any clarifications. LOL
<< Which means either my understanding of the rules are messed up or my math is incorrect. >>
Or both!
<< My math must be incorrect but:
<< 9 active tasks out of 32 lines: 9/32*100= 28%
<< and
<< 23 active tasks out of 29 lines: 23/29*100=79%
<< So, isnt there higher chance of a task on the last active page being selected since more of the lines are open to being selected? >>
Yes, you are right - your math is incorrect. What you have worked out is the chances of a task being selected if there were no "slide" rule. And the same applies to all your other calculations.
But since there is a "slide" rule your calculations are irrelevant.
The correct answers are that there is a 100% chance of selecting at least one task on the first page whenever the randomizer lands on that page - this is because the "slide" rule always selects a task on the same page that the number lands on.
On the last page there is a 100% chance of at least one task being selected if the randomizer lands on one of the 29 used lines.
Since I have 9 tasks on the first page and 23 tasks on the last page, the average chance of a *specific* task on the first page being selected is 100/9 = 11.1% and the average chance of a *specific* task on the final page being selected is 100/23 = 4.3%
Note that I talk about the "average" chance, as the individual tasks have different chances according to the length of the slide leading to them.
If you can't follow the logic in my previous post then I suggest you try an experiment.
List the numbers 1-32 and see how many throws of your randomizer it takes before you delete the last number from the list using these two different methods:
1) If the randomizer lands on a deleted number you "slide" to the next undeleted number and cross that off, circling back to the beginning of the list when necessary (i.e. the number after 32 is 1).
2) If the randomizer lands on a deleted number you throw again until you land on an undeleted number.
HINT:
You can print off a list of random numbers from RANDOM.ORG which will save you time and make it easier to count the number of throws.
<< The slide ensures that ‘landing on a crossed off item slides you to the next active task’. Makes sense in terms of proximity. But if I’m moving FORWARD in the notebook to the next active task, doesnt that mean that items remaining on NEWER pages have a high chance of being selected? >>
Here's how the "slide" rule works. If you land on a completed task, you slide forward to the next unfinished task. However, if you slide all the way to the bottom of a page, you continue sliding from the top of THAT SAME PAGE, rather than sliding to the top of the next page.
So, as Mark said, if you land on page 1, you are ensured of selecting a task on page 1, whether you land there directly with the randomizer, or by sliding.
Mark has already explained this, but maybe it will help to get it from a slightly different perspective as well.
I'm only now noticing that you and mark mentioned that slides can circle you to the beginning of the same page like 4 times.lol For someone who didn't read the instructions carefully (myself) it is very confusing to find the bias. Now I get it.
P.s. I believe its the way the post is written. It seems like you have instructions, an example and then notes. But that key instruction is hidden between two examples. So it could be overlooked like I did. I'm talking about this part : " Slides work slightly different from counting. If a slide takes you to the end of the page, you circle back to the beginning of the SAME page. So if “Performance Reviews” in the example had already been done, you’d have circled back to “Email” at the beginning of the page."
Anyways, now that I get it, seems pretty cool. I'll be trying it (correctly) tonight.
Do you write proposals, contracts or specs as part of your job? You are quite articulate.
But I think that's the first time anyone ever called me articulate! Usually it's "long winded" and "can't you up-level that?" and "can't you write that shorter?" LOL!
When you write a thorough post, I appreciate the details. You make things easy to understand. None of your words are superfluous.
I, on the other hand, am not graced with your talents. My ramblings sound addled....
This makes me wonder : it is theoretically possible to completely strikethrough a page in the middle of the notebook while there are still unstriked items on older pages. (A trivial example on how it is possible is to land on the first item of a page and roll ones all the way to the bottom) Did it happen to anyone who tried the system so far? It did not happen to me in three days.
(Just out of curiosity)
I'm asking as most electronic mediums do not have pages as in a notebook. That has been a problem for me trying to do AF and sf through an app. Any suggestions?
Has that happened to anyone with the official system? A block of crossed-out tasks at the end of the page that you can't seem to jump over, so you're stuck on the same page for long enough that the system loses the random feel?
Until just now I thought that sliding backwards instead of forwards would work, and keep a bit of pressure on the older tasks like the official system does, without the need for pages or the often-missed slide to top of page rule, but it's even more prone to those long clean stretches.
Once again, Mark's system works best as written.
(Wishing the universe would stop playing whack a mole with me for long enough that I can find my list. Even with the small rubber mallet, it's getting annoying.)
<< Has that happened to anyone with the official system? A block of crossed-out tasks at the end of the page that you can't seem to jump over, so you're stuck on the same page for long enough that the system loses the random feel? >>
I think it's unlikely that this would happen for the simple reason that if you had a long block towards the end of the page there would almost certainly be only a few tasks left on the rest of the page. Your attention then gets grabbed by whether you can completely clear the page that visit or not.
<< This makes me wonder : it is theoretically possible to completely strikethrough a page in the middle of the notebook while there are still unstriked items on older pages. >>
Yes, it's happened to me. It's quite possible, though it doesn't happen very often.
<< I'm wondering if having pages gives any advantages over one long list (one lone single page). Does the sliding possibility on each page have a stronger bias over say sliding at the end of one long list? >>
I don't think one long page is necessarily worse than dividing the list into pages, but there is one problem you would have to overcome:
Because there would be only very rare slides from the last page to the first page (due to the constant adding of new and re-entered tasks), the first task on the list would nearly always have to be hit exactly by the randomizer. If you did the exercise I suggested earlier, you will know that it can take a very long time for one specific number to be hit (it took me 122 throws to clear all 32 numbers). Any task that finds itself at the beginning of the list will therefore find itself at a severe disadvantage.
I don't think that is an unsurmountable problem, but you do need to be aware of it.
<< there is one problem you would have to overcome >>
I think you could address that issue by sliding backwards instead of forwards. But that introduces new problems... Since you don't have pages, you can't "clear" pages. This would result in large blocks of completed tasks. Your random number range might not be big enough to cross these large blocks. Example: you decide to generate numbers from 1 to 32. But you have a large block of completed tasks, say 35 of them. Thus you can't cross this chasm - you'd always be sliding backwards to the task immediately preceding this block. You'd basically be forced to work backwards through the tasks preceding this block. Maybe that's OK. But I'd guess it would introduce resistance to the system because the random nature of task selection is essentially removed, till you clear out all those tasks.
Another problem introduced by a pageless version of the system: You'd need to choose an arbitrary range for your random number generator. Maybe that would be OK. But what would be the best range? You'd want it high enough the avoid the issue described in the previous paragraph, but not so high that counting tasks becomes tedious.
Because of these kinds of problems, I suspect going pageless would totally change the dynamics of the system, and you'd need to rewrite the rules completely to achieve a similar outcome.
For a notebook, its neat. However, I'm concerned with the pageless issues described above. Chris's and Seraphim seem to have a solution.
Going backwards on a slide as Seraphim described still has that chasm issue.
Switching directions based on even/odd throws as Chris suggested seems as if it would even things out a bit. Though, Im guessing this adds a layer of overhead, remembering to switch directions
Are there any other solutions that can even the bias between page (notebook/analog) vs pageless (one long single list/electronic/digital) versions Mark? I'm asking as I know it can be annoying when people bring up the notion of tweaking your system and you said that it probably can be adapted for electronic versions.
How would you adapt the system for electronic use?
> How would you adapt the system for electronic use?
I'm still in early days of using the random method, but here are some ideas I've used in the past, using a simple text editor (actually, I'm now just using the default Notes app on the Mac/iPhone/iPad):
- Add a blank line every N number of items to mark the start of a new page
- When I tried with longer pages, I would just “open a new page” by pasting N empty bullets as placeholders for the list items
Currently I'm doing one long list because the number of open tasks I have is quite small (twenty-ish)… I few things I did:
# What random number to use?
I started to randomise with around 1/3 or 1/4 of my starting number of tasks. Since I had 20 tasks in my initial brain-dump, I'm just rolling a dice (1-6) to select a task (the physical action of rolling a real dice is turning out to be more fun than I thought :D)
I remember Mark mentioning at some point that he has approximately 90 tasks open and since he was randomising with 32, I figured that would be a good enough ballpark ratio for getting started.
# Hard to hit first item?
Because there wouldn't be any pages, I though of leaving 3 scratch lines before the first item (half of the dice) to make some sort of cushion for the wrap around… but luck has this things and the first draw I got was 1 so I started immediately on the first one :)
One key though is to try to avoid seeing the entire randomized list at once, because it is tempting to let your eyes wander to the tasks in cells A2, A3, A4 etc, and then a familiar feeling of procrastination kicks in. Usually I make cell A1 (the first task) very large so I can only see the first task and HAVE to do it.
This sounds like it would be very easy to implement in a spreadsheet. On Sheet 1 just list each task on its own line in column A. On Sheet 2 have a macro which generates a random integer between 1 and LastRow. You could even have conditional formatting for all of Sheet 1 Column A such that if the random number shown on Sheet 2 matches the line number then the line has a yellow background. This will automatically highlight the selected task on Sheet 1.
Once the task is done simply delete the row, the remaining tasks will always be sequentially numbered and selected directly by the randomiser. Sliding won't crop up.
Thanks for the diversion. I downloaded the 30-day-free-trial of CP NoteBook.app and it's pretty neat. I especially like the different grids - e.g. Engineering Pad. But I realized that the formatting keeps changing, depending on the window size on the screen. Is there any way to keep it consistent on screen and also have PDF output that matches the on-screen look (WYSIWYG)?
<< Once the task is done simply delete the row, the remaining tasks will always be sequentially numbered and selected directly by the randomiser. Sliding won't crop up. >>
That will result in the odds being equal for every task on every throw. There's nothing wrong with that as long as you realise what it entails.
The sliding means that the system clears all tasks within a fairly short time (the exact length depending on the length of the list). Without sliding there is no such guarantee. A task which has been on the list for a week will have no more chance of being selected than a task which you put on the list five minutes ago.
It is easy to copy in the spreadsheet. Hidden column B contains the number 1 for each task entry. Adding a new entry automatically populates column B with the number 1. Each use of the randomiser macro increments column B. The selection algorithm factors in the number in column B, so an entry with the number 2, 3, 4, ...has increasingly more chance of being selected than an entry with number 1.
This weighting will ensure that the longer an task hangs around for, the more the selections will be biased towards them.
Although I don't use any AF lists, I thoroughly concur with your idea of engaging a flexible attitude when approaching work. Mark's website is loaded with many tools and tips which I keep at the ready. I'm more interested in getting the job done than trying to fit the situation, my mood and/or my abilities into to a particular system. Engaging a flexible approach has ultimate less cognitive overhead unless you're one of the lucky ones who's life's demands and aspirations and one's own abilities remain fairly constant. I only wish…
<< Correct, but wasn't that the original benefit, with older tasks having had more chance at being selected previously? >>
No, it was designed with sliding right from the beginning. In the first "Shades of the Diceman" General Forum thread Simon described how he selected a page number and then a line number randomly and if the line was crossed out he moved to the next active task. I pointed out that this wasn't fully random as it gave preference to the older tasks. I then adapted his method to produce the one in this blog post.
<< I thought sliding was just an artifact of the written medium with the happy coincidence of giving undone tasks next to done tasks additional chances of being completed by essentially giving them multiple numbers that select them. >>
No, I realised that sliding was an ideal method for avoiding the problems raised by having equal chances. There's no reason why sliding has to be confined to the written medium. It's just a matter of not deleting the lines that have been crossed out - or using a method like the one you're describing.
<
Good. I'm glad you've understood the problem with the way you were planning on doing it. Usually it takes more than 120 throws to clear every one of 32 numbers without sliding, but exactly 32 throws to clear them with sliding. So it makes a considerable difference to how long some tasks will hang around on the list.
1. Google spreadsheets/ Excel.
-line numbers=rows
-spreadsheets =pages
-workbook=notebook
-use randomizer
-cross out using strikethru or highlight (grey is good)
2. Toodledo: Lists
-rows=lines (max is 30 for free user (perfect!))
-Lists=pages
-'Lists' tab= workbook (automatically sorted)
-use randomizer
-cross out using check
Thoughts:
In both 1&2, the system is pretty much perfect. No automatic disappearing or re-sorting of completed items and the rows remain as they should as if written on paper.
In Spreadhsheets, items are written one per line top to bottom. In Toodledo, items are written one per line bottom to top.
In Spreadsheets, it feels like a spreadsheet managing tasks and a bit more cumbersome to add items to. Whereas, Toodledo lends it self to task management, getting tasks in and out and filteres etc. (If needed, it can be very simple or very complex.)
FYI:
Both are great, but I must say that I'm impressed with Toodledo's changes since I left it. I left it because I switched from ios to android. But have now found out that android was made avaiable 5 days ago. So Its pretty much very accesible.
There are 4 tabs- Tasks, Notes, Outlines and Lists. Some are pre populated for you. Very impressed and excited to use everything in one system.
Not to skew the topic, but wanted to add:
The Toodledo List tool also makes it possible to try any of MF's page based systems. AF, SF etc.
Worth checking out. But it should be noted, that this feature is specific to the web from what i can see and not for the mobile apps on ios and android.
Ubi: Regarding Circus Ponies, I've just started the trial myself, but I don't see font sizes changing when adjusting the window size. PDF output also preserves the fonts for me. I have different fonts in my pages because I have clipped or copied data from different sources, and they are all preserved in the PDF output when I tested it.
I hope I'm understanding your issue correctly. Support is quite good, so maybe you could check with them.
Rolling a (virtual) dice has completely eliminated my procrastination problems. Who would have thought? Also, I may be doing it wrong, but as I'm using a gtd-setup in emacs orgmode, I roll the dice on my next actions list, which is constructed from my active projects.
However progress on my projects is so incredible fast now, I'm really hesitating changing my setup.
Thank you Mark!
Great to hear that!
Regarding Circus Ponies NoteBook.app, my issue was how the page layout changes when you resize the window on the screen. There seems to be a default size when you open a new NoteBook, but if you use, for example, the Engineering Pad style, the number of lines and grid squares changes as you resize the window, and there's no obvious way of restoring the default look. Also, if you put a lot on a page, it scrolls instead of rolling over to a new page. The bound-paper notebook effect is broken, therefore: there's no direct correspondence between what is onscreen vs what you would see if you added the same content to a physical notebook, or to the number of pages you would get if you printed out the whole thing.
I guess this is what they intend. There are several postings on this topic on the CP support site. I'll play around with it for a few more days, but doubt I will pay the $50 or so that they're asking for a license.
We should probably start a new thread on this app in the General Forum, if anyone is interested, instead of continuing to discuss it in these blog comments. . .
I know 'tweaking' Mark's systems can sometimes lower effectiveness, however I'm considering doing some (urgent or context relevant) tasks from the list out of randomisation and marking them as such to indicate this with a second dot to the right of the item. I wonder if this would create any drawbacks?
No, I haven't tried that. Obviously it would be critical what range you set the randomizer for. At the two extremes:
1) If you set it for between 1 and 2, then the effect would be only slightly different to just ploughing through the list in the order it was written.
2) If you set it for between 1 and n, n being the total number of unactioned items in the list, then it would be completely unbiased, i.e. every task would have an equal chance of being picked.
What do you think would be the right setting? And what are the factors that should be taken into account?
Just another thought on adding priorities to the calendar. That's what I do - populate the calendar with items due on a particular day. I also use the calendar as a tickler.
The last couple of work days I have randomised the items on the calendar as well. For example this morning I had three appointments and six 'all-day' items I am committed to doing today. First thing I cleared off any prep for the appointments. Then I created a short list in the beginning of my notebook consisting of all the remaining 'today' items from the calendar. I set the upper bounds of the randomiser to the length of the list and work the mini-list according to Mark's rules. I'm down to the last two now. It breaks down a little as the list drops to one or two. As I complete work for the day any follow-up items that aren't needed today go on to the calendar if they are time-bound, or on to my master list. Once I'm done with the daily stuff I'll turn to the master list and spend the rest of the day working that.
I find it helps break down a little of the resistance to the items on the calendar, just as it does for the items on the master list.
Matt
<< The last couple of work days I have randomised the items on the calendar as well. >>
Interesting thought. I don't think it's what you meant, but I wonder if anyone has tried making a list of the tasks to do within a week and then setting the randomizer to produce a number between 1 and 7 (or 1 and 5 for the working week) to decide which day each individual task should be done? The same principle could be used for a month, and even for "someday/maybe" tasks.
I have not tried this myself, and probably won't for the time being, but if anyone does want to try it I would be very interested to hear your experiences.
<< I wonder if anyone has tried making a list of the tasks to do within a week and then setting the randomizer to produce a number between 1 and 7 (or 1 and 5 for the working week) to decide which day each individual task should be done? >>
That is an interesting thought. I don't plan ahead on my weeks like that, I simply have reminders in the calendar and my main list of tasks, so I can't readily try it. I suspect there may be too many dependencies to allow randomisation. And then, once tasks are assigned to days, you would end up trying to execute a pre-planned weekly schedule.
I'm finding that the random selection is working well when the choices are already structured and there are known parameters to the list. That way I can relax and go with whatever comes up. The parameters can be as broad as 'nothing critical today, do anything on the list' or as narrow as '5 critical things to do today', but they are defined and I can roam freely within the limits.
I did try setting my daily exercise randomly to give an element of surprise and variety. It didn't work because the various types of exercise available to me are dependent on each other. I couldn't, for example, end up with 7 days in a row of randomly assigned very high intensity circuits.
Matt
<< I couldn't, for example, end up with 7 days in a row of randomly assigned very high intensity circuits. >>
Though this is exactly what the exercise application Sworkit provides one with.
Mark Forster answered: << I cross it out and re-enter it at the end of the list. But you can experiment with other ways if you want. >>
( http://markforster.squarespace.com/forum/post/2275650#post2276116 )
Mark - Is this still the method you are following for this situation?
//No, I haven't tried that. Obviously it would be critical what range you set the randomizer for. At the two extremes:
1) If you set it for between 1 and 2, then the effect would be only slightly different to just ploughing through the list in the order it was written.
2) If you set it for between 1 and n, n being the total number of unactioned items in the list, then it would be completely unbiased, i.e. every task would have an equal chance of being picked.
What do you think would be the right setting? And what are the factors that should be taken into account?//
I think the answer is that for a DIT-like feel, the ideal setting would be the number of tasks added yesterday.
<< Mark - Is this still the method you are following for this situation? >>
Yes.
<< I think the answer is that for a DIT-like feel, the ideal setting would be the number of tasks added yesterday. >>
I'm tempted to have a go!
I think there is another downside to 32 numbers, which is that it may not succeed in clearing all the early tasks as quickly as we would like. This is because it takes a lot of throws (120+) to clear every number between 1 and 32.
Perhaps someone would like to try?
How's it working out for you?
Generate a random number between 1 and 25. 20-25 means do the first task on the list. 1-20 means move forward by that many tasks from your last task that was selected in this manner. Do not count completed tasks or the oldest task in your 1-20 cycling.
It is working well with the randomizer set at 14 and OmniFocus for the digital version.
Right now I have three "pages", called projects, in OmniFocus, with 27, 24, 25 total tasks per page.
I went digital on Feb 1, out of town Feb 2, worked on list Feb 3. What is left is 9, 11 and 19 on respective pages. The system is working well for me and I am at least touching things I would normally be letting go. Thank you.
http://markforster.squarespace.com/forum/post/2286299
Mark suggested crossing them out and rewriting them at the end of the list, which is clear. But what happens then? Do you just continue to the next task on the list and use that instead, or generate a new random number and start counting from the next task?
Thanks
If I can't do it at that moment or it's too late to start it (>one hour), I leave it where it is and count it as a slide as if it was crossed out. That way the list doesn't unnecessarily grow. My list is daily which is fed from the calendar and weekly list.
You'd probably do better to follow Seraphim's advice. I'm a really hard case so I need to batten down the hatches to greatly reduce my escape options. When I'm dreading work, I treat myself like a cattle being prodded down the shoot for slaughter. It sounds exaggerated but that's what dread sometimes feels like in my head. The randomization does wonders to reduce resistance and the dread. Mark has several great work arounds but the randomization method really does the job when I need the assistance.
I hope it helps you. Some of the folks say that their resistance actually disappears. I'm not that lucky but it sure doesn't reduce it enough to help me get my day's list done most days.
It seems to me the dice allows all options to be emotionally neutral so that none is any more meaningful than another. I wondered if the downside was that it cancels sensitivity to right-timing?
I can't speak for others, but the matter of right timing is resolved when I create the daily list. The trade off is not jumping right into the enjoyable work so that I will have willingness to also do the less enjoyable work. The dice helps to prevent overwhelm on particular work because I don't know EXACTLY WHEN I'll have to start it and I also have chances to do work I prefer. Usually I do my list however I wish just like Mark taught in DIT. It doesn't matter how I complete it so long as it gets done. The randomizer helps to neutralize overwhelm. Also when I get a preferred task, it's even more enjoyable because of the relief I feel that I don't something onerous. Also, I don't spend the entire day on the WILL DO list. There's lots of flexibility. Win-Win
Excellent thinking! That sounds a really good way of doing things.
1) Keeping the list reasonably short is essential. At the moment my list is 39 items long and it's working brilliantly. I think it could be a bit longer than that without too much problem, but a long list is too slow to keep the work moving.
2) I've experimented with all sorts of different ways of improving the system, but so far have not found one single alteration that is better than the rules as written in the blog post.
3) The easiest way to monitor how well your list is keeping up with your work is to monitor two statistics: 1) the age of the oldest item on the list; and 2) the number of items there are on the list. Since the random method reduces friction and procrastination to negligible levels, if you can't keep up with your work, then the only solution is to reduce the work.
4) I find this system works best with larger tasks than I use with normal AF or FV. So rather than have a lot of small items, I tend to combine them. For example I would have "Read blogs" rather than list all the blogs I follow; "Finance" rather than all the different actions I take in respect of my finances.
have not found one single alteration that is better than the rules as written in the blog
post.>>
Agreed.
Here it is:
https://docs.google.com/spreadsheets/d/1YrWsENLJ5BfPxEmC6WfZ-XtnFpjXNN4mtE_HuqOPcUA/edit?usp=sharing
If you want to see how it works, please enter only in Yellow cells otherwise you may erase the formulas. Feel free to copy it and use for your own list. At the moment I set the page size to 10, but that can be changed in the hidden columns.
Your spread sheet is cool, hope I didn't break it by using it a few times. I tried to export it to use locally in Excel but it didn't work, some error. Are the formulas tricky to recreate?
Not sure who played with it, but I have fixed it. Just make sure you change yellow cells only!
It should be straight forward to recreate in Excel as all the formulas used are compatible, just make sure you use CRTL+SHIFT+ENTER when entering ARRAYFORMULA formulas in Excel. You would need to add conditional formatting in Excel too.
Also I think Google Drive can convert sheets to Excel though I haven't tried it yet.
Any thoughts on the upper random number. You work on 1-32 and so do I as I am working with a notebook with those lines per page but someone posted at 14 which would give a greater feel of moving through the list and back to early items but not sure if it would make much difference in practice
<< Any thoughts on the upper random number. >>
I think this is just a matter of experimentation to find what suits you best. I've found 32 suits me fine, but I haven't tried any other numbers. It just happens to be the number of lines in my notebook.
One thing to bear in mind is that the lower the number the slower you will circulate through the list.
Fewer than that = it can feel like you are getting "stuck" on a page, not moving fast enough forward to where the newest, freshest tasks are located.
More than that = you have a much higher chance of having only 1 "stop" per page, which really weakens the power of the "slide" rule.
http://www.routeloops.com/
I've been looking for a site that does that. So many thanks indeed!
"No, I haven't tried that. Obviously it would be critical what range you set the randomizer for."
To be honest, I was stumped on how to answer this and decided to percolate on the problem, which is why I was silent for some time Austin's suggestion on using the number of items added the day before brought forth the germ of the solution for me, and it clicked: we can actually let the system decide what is the range for the randomizer (let's call it N).
N =
A. First day
1. Make your list, then mark the last item. Count all the unactioned items. This is your N (range of the randomizer) for the rest of the day.
2. Pick a random number from 1 to N inclusively, then count from the first unactioned item down each unactioned item until you reach that unactioned item corresponding to the random number. Do that item, then delete. If needed, rewrite at the end of the list. All new items are also added to the end of the list.
3. If you reach the end of the list counting, continue counting from the first unactioned item.
B. Subsequent days
1. At the beginning of the subsequent days, count the number of unactioned items before your mark yesterday, and also the number of items after that mark. Whichever is higher will be your N for that day. Make then a new mark for the last unactioned day from yesterday.
2. Repeat the rest of the steps above.
I had to go back and search for your original suggestion as I couldn't remember what it was, so for the benefit not only of myself but anyone else who's following this, here's what you wrote:
"... have you tried always starting counting down from the first unactioned item, and only counting the unactioned items? Theoretically, that would even focus more on the older items, almost to the point of making it DIT-like."
Yes, I have now tried it. And the one thing that came out of my trial is that the range you set needs to be quite small. I found 1-10 worked reasonably well, but if you get too much above that you get the problem you always get if you have equal odds, which is that a few tasks won't get picked for a very long time.
I think what you need to do is experiment with various ranges to see what works best. You don't have to use real tasks for this. You can simulate just by putting x's on lines on a bit of paper.
Since I don't want to use the system electronically, I've gone back to sliding as I much prefer it.
Have you come up with a way of dismissing tasks with this system. My thought is that if you refuse to do a task, you highlight it. If you refuse to do a highlighted task, you dismiss it. I wonder what your thougts are on this. Is dismissal even necessary?
I haven't actually found a need to dismiss tasks yet. I've find the system removes so much of the reluctance to start a task, that I haven't yet refused to do one.
You can of course always remove any task that you decide shouldn't be done or doesn't need to be done any longer.
You always start counting from the next line after the task you've just done.
In short, are there any dismissal rules for this system
Your post did get published (it's five posts back from this one) and I replied to it three posts back.
My system is a bit different than marks, but today I used the randomizer method to work through my daily list.
I have to say that I'm REALLY impressed with how well it did at diminishing my resistance to tasks. I'm going to keep on using it.
Thanks,
brett
I found that FocusPad (app.focuspad.ws) is perfect for this in electronic form
However, after tinkering around, I found out that it is actually easy to adapt this system to my BlackBerry Z10 Remember app, which actually syncs to my Evernote account so I can look it up anywhere. How I do it can also be done using the Evernote program/app itself and even any word processor.
> Open a note and use Numbered List format to list your tasks, one task a line. Once you have entered your 32nd task, skip a couple of lines, turn off and turn on Numbered List format. This will reset the numbering of the list to 1, and thus you have simulated a page of 32 lines.
> To pick a task, highlight the task by changing its font color.
> When you are done with the task, select and cut the whole task. The result will be that the line will keep its numbering but it will be blank. If the task is unfinished or recurring, it can then be pasted at the end of the list. Make sure to revert the font color to black.
I was surprised how easy this was to implement. In fact, I added another feature to how I do this system, integration of projects, because of how the Remember app and even the Evernote program/app is.
> Projects are entered to the system by using bold font format on the task.
> The projects have their own notes with either of two list formats.
>>If the project is a bunch of tasks to be done in order then the list is in Bullet List format.
>> However if the project is a bunch of tasks that can be done in any order, then I use Numbered List format and do the project randomly like I would the main list.
"I see how this approach gets a payoff of results but how do you build in time to develop clarity about the nuances of the situation and possibilities?"
This system has no utility whatsoever for urgent tasks, so if you need to do something right away, drop the system and do what you have to do.
If you need to take a breather from your tasks, seeing that you need to relax and add space to look at the bigger picture, then do that and drop the system for now.
On the other hand, the system I found has a calming and strengthening effect on me, in that I can use this to build up my confidence that I can do stuff before doing the scheduled stuff that I need to do.
Sometimes that is all you need, the confidence to do what you need to do, and that can also give perspective on the things you have to do.
<< This system has no utility whatsoever for urgent tasks >>
At the following thread, we've discussed some ways to adapt Randomizer to help with urgent tasks.
http://markforster.squarespace.com/forum/post/2295850
<< how do you build in time to develop clarity about the nuances of the situation and possibilities? >>
No problem at all. Make a task of it. Maybe just "Think about my work" or "Examine possibilities" or however you want to phrase it.
To expand the point I suppose I can say if I want *changes*, rather than just productivity on the same hamster wheel, the more different the change is than what I do normally, then the more inner actions will need to appear on the AF list. Change doesn’t happen just from outer actions, or because we wish for it or want it but only through taking different inner actions - even if it is the action to not believe a thought, imagine a different interpretation, pausing for insights, affirming differnt thoughts, noticing what's better ...
I have several tasks that I am "waiting" on but are ultimately still my responsibility. What do I do with them?
http://textmechanic.com/Random-Line-Picker.html
There are many cool tools at this site. This one allows you to input (or paste) a list. It then will pick one item at a time. I like it when I have a small list of things I must do and it assigns me one at a time.
I haven't figured out any way of integrating the sliding concept into this tool, however.
It does have a graphic test of your browser's ability to pick randomly - which seems to work.
Natural 20: Custom Rolling Dice
http://itunes.apple.com/US/app/id517523153?mt=8
I have spent many hours over the last few weeks writing a web app that follows this method "to the T." I have a few kinks to work out, but I'm wondering if any of you are interested in using it. I built the prototype to work for just a single user, but I don't want to spend any time on the authentication piece unless some of you are willing to give it a try.
I may post a short video sometime, but for now, here's a description:
1) Single-page AJAX application (node, angularjs, mongodb, express, passport, bootstrap, etc.)
2) Configurable "per page" amount
3) Adjusting "per page" changes pagination immediately
4) All rules apply (sliding, choosing next task, etc.)
5) You can do a task out of order, but you have to enter a command first (pretty neat really, it makes it less convenient to skip ahead and cross something off out of order)
6) Total tasks remaining is easy to see
7) Done vs Total per page is easy to see
8) Per page minimum and maximum hardcoded by me (any ideas on this? I have 5 as the minimum and 40 as the maximum)
9) Responsive design should work on all devices
10) Convenient "down arrow" button to complete a task and create a copy at the end of the list (for when you're "done for now" with a task)
11) "Easter egg" commands... you'll have to wait and see
I guess that's enough for now. If there's any interest I'll spend some time making it ready for public consumption.
Let me know!
I showed this to some colleagues and they wanted to see a few enhancements:
1) history of tasks
2) edit a task's text
-Adam
Your application sounds great! I for one would love to try it out...either running on a site somewhere, or installed locally if you don't want to add multi-user login features. Is it available on github?
Thanks,
- Erik.
Sounds neat!
I shouldn't change for a while yet, other than fine-tuning how I work the list and prioritize things within the system.
A few things that none of the other systems seem to have:
Change the date done. If I do something after computer-off time, I want to be able to record it the next day, or even a few days later. This is important for tasks where you want a history (Which day did I do it? How many days this week?) and when the next time depends on when it was done last.
Support for things I hope to do several times a week. The tasks would still show in the main task list for Randomizer to choose, but with more information. Maybe how many times you've done it so far this week. If the task is "work out 1st time this week" and it's Thursday, I'm in trouble. Also a report of some type, maybe like Joe's Goals.
A Hot List capability. Not tons of priority levels, but a way to flag critical things. If the day is busy, just limit selection to the hot list. If the day is light, select from the entire list.
Future start dates. Due dates.
Bonus points for email integration. Send email to the list and it gets added as a task.
1. Say I start with 31 tasks on one page (that has 32 lines). I randomly generate 7, which lands on a recurring action. I do the action, cross it off, then rewrite it in line 32.
2. I generate another random number, and get 21. I do some work on the task, but do not complete it. Nonetheless, I cross it off and rewrite it...I assume on the first line of the next page.
3. I need to go buy milk at the store, so I enter it on the second line of the second page.
So here is where I am confused and need answered:
Q1. Does the random number generator limits stay fixed at the total number of lines on the one page each time you use it (i.e. 32)? Or will it grow to match the exact number of tasks that you have spanning over multiple pages (34, which comes from 32 on the first plus 2 on the second)?
Q2. If it stays the same, do you simply treat each page as a different list and then move on the next page when you want? What is the criterion for moving to the next page? Do you use the random number generator for each page that you are on individually?
Thanks for your help as I try to figure it out. It seems like a promising technique.
<< Does the random number generator limits stay fixed at the total number of lines on the one page each time you use it (i.e. 32)? >>
Yes.
<< ... do you simply treat each page as a different list and then move on the next page when you want? >>
No, you treat the whole list as one continuous list. So if you are on line 20 of Page 1 and you throw a 25 you count to the end of Page 1 and then continue on page 2. So you would land on line 13 of Page 2.
If your count brings you to the end of the list, then you just rotate back to the beginning of the list. Ignore empty lines on the last page.
The only time that the end of the page is relevant is when you land on a line which has a deleted task. In this case you "slide" until you reach the first active task thereafter. If you reach the end of the page before coming across an active task, then you carry on sliding from the beginning of the *same* page. The reason for this is that otherwise one could not guarantee that the first line of the first page would ever get hit.
Remove pages on which all the tasks have been done.
I hope this helps. It's best to try the rules as best you can for a few days then re-read the rules carefully to make sure you are doing it right.
For example, I really liked this "Random Time Management", which I have adapted and used along with another method. Now Mark is talking about the "Spinning Plates". Does that mean Mark abandoned this method, or is he trying another method for another purpose?
<< Does that mean Mark abandoned this method, or is he trying another method for another purpose? >>
It means he keeps trying out new ways of doing time management, because every idea that works may then become a building block for better time management methods in the future.
You are welcome to use his ideas however you wish.
Thank you for this, Mark
Do we need a random task generator system for a random task generator system?
I will have to figure out how to incorporate this concept and make it my own; I seldom have more than 10-15 tasks (projects) active at any one time... Perhaps there's stuff rattling around in my head that needs to be captured. Wait! There's a new task!